Method of operation
Testing is a measure to provide insight into the quality and the related product risks of a system or package when it
is taken into production by an organisation. Since there will never be an unlimited quantity of resources and time, it
is important to determine in advance which system parts and characteristics require additional or less test effort.
Well-justified choices have to be made in this context. One instrument to determine areas of concern for the test is
executing a product risk analysis ( PRA).
Executing a PRA consists of the following sub-activities:
-
Determining participants
-
Determining the PRA approach
-
Preparing session/interviews
-
Collecting and analysing product risks
-
Completeness check
These steps are described in detail in Product Risk Analysis. It must be taken into account that a great number and variety of participants are involved in a
master test plan, which means that the risk analysis may be less detailed. The participants are often acceptants, but
also other information providers as discussed in Understand The Assignment (MTP). For instance, test goals often differ and a division into object parts varies for technical
management and users and is usually dependent on a characteristic. Functionality, for instance, has another division of
the system into object parts than performance or security. Quality characteristics are often chosen for
characteristics, but testable aspects can also be used – such as installability, multi-user, regression, etc. A
possibility is that a PRA session may be combined with (part of) the subsequent activity, Determining the test
strategy.
Products
-
The risk tables with the test goals and possible object parts with risk indications for each characteristic,
managed separately and optionally laid down in the master test plan.
-
The PRA total overview with characteristics/object parts with risk class, defined in the master test plan.
Techniques
|
